Summary

When I attempted to use the changes from #10389 I ran into 3 minor issues which this PR attempts to fix.

• Creating a bank transaction would always use USD as currency as there was no currency_id field in the bank transaction body. Now all available currencies are retrieved via InvoiceNinja's API and the currency for a bank transaction can be adopted.
• The API call for matching bank transactions to a payment expects a payment_id param. This was mistakenly named paymentId.
• The API call for matching bank transactions to a payment also expects an array of transactions like this:

{
  "transactions": [
    {
        "id": "{{TRANSACTION_ID}}",
        "payment_id": "{{PAYMENT_ID}}"
    }
  ]
}

The current implementation only provided one transaction object which didn't satisfy the InvoiceNinja API.

Related Linear tickets, Github issues, and Community forum posts

Follow-up of #10389

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)